Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 6d164eb67b2e05b067a26d3fb5d983ff0b44ca84c4a1476f6c02c041f748484c

Tx prefix hash: c789f871c573af4280c19b69d05acaf34456dec1265bb04757b0d7827997ea00
Tx public key: 67b49b1dd34a1c7e5eb4fdcc4a1f1d76e877f661d484ab357c6a0499a5b6f696
Timestamp: 1640821889 Timestamp [UCT]: 2021-12-29 23:51:29 Age [y:d:h:m:s]: 03:000:19:17:28
Block: 406359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 779560 RingCT/type: yes/0
Extra: 0167b49b1dd34a1c7e5eb4fdcc4a1f1d76e877f661d484ab357c6a0499a5b6f69602110000000106faf294000000000000000000

1 output(s) for total of 27.642460612000 dcy

stealth address amount amount idx
00: a9dfb5d72499350ff27ae72dca55d91e0bb2e95bb9c9e83a7d8e090091d21cb5 27.642460612000 807195 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 406369, "vin": [ { "gen": { "height": 406359 } } ], "vout": [ { "amount": 27642460612, "target": { "key": "a9dfb5d72499350ff27ae72dca55d91e0bb2e95bb9c9e83a7d8e090091d21cb5" } } ], "extra": [ 1, 103, 180, 155, 29, 211, 74, 28, 126, 94, 180, 253, 204, 74, 31, 29, 118, 232, 119, 246, 97, 212, 132, 171, 53, 124, 106, 4, 153, 165, 182, 246, 150, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8