Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 081821302d0dd1091fbf64959b8f3551c0c61c8b2710d8177978cf7eed7f1dcb

Tx prefix hash: 3a59b33ca66f1ceca6e7fc415299f18bc86105e7b4ee41735d9feb194a215c9e
Tx public key: 6ca45184e80636b9fbcc7d02593734e2dba5bb627af912c9edbcb2a47d115067
Timestamp: 1687289231 Timestamp [UCT]: 2023-06-20 19:27:11 Age [y:d:h:m:s]: 01:213:07:58:50
Block: 786615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413824 RingCT/type: yes/0
Extra: 016ca45184e80636b9fbcc7d02593734e2dba5bb627af912c9edbcb2a47d11506702110000000533af99f4000000000000000000

1 output(s) for total of 1.519211066000 dcy

stealth address amount amount idx
00: 77740804779cac7060bb0483e64485292e055dce05bc64167e3a890fd8a6e6e5 1.519211066000 1236616 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": 786625, "vin": [ { "gen": { "height": 786615 } } ], "vout": [ { "amount": 1519211066, "target": { "key": "77740804779cac7060bb0483e64485292e055dce05bc64167e3a890fd8a6e6e5" } } ], "extra": [ 1, 108, 164, 81, 132, 232, 6, 54, 185, 251, 204, 125, 2, 89, 55, 52, 226, 219, 165, 187, 98, 122, 249, 18, 201, 237, 188, 178, 164, 125, 17, 80, 103, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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