Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bb15e8f8cd5306d1df489968d0d0a9f3ca32dd1b241df5204ef340386050694

Tx prefix hash: 54211fa64c238fb3e0160c6a530d245fa87e38d69da00d5042369c4a69888151
Tx public key: a3e7316f6e6d01ddefd73d09d4e6c6d512a4a00548c5b7257df4efcf3c74439b
Timestamp: 1672697321 Timestamp [UCT]: 2023-01-02 22:08:41 Age [y:d:h:m:s]: 02:145:23:40:48
Block: 666260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 626059 RingCT/type: yes/0
Extra: 01a3e7316f6e6d01ddefd73d09d4e6c6d512a4a00548c5b7257df4efcf3c74439b02110000000152542ceb000000000000000000

1 output(s) for total of 3.805432343000 dcy

stealth address amount amount idx
00: 5163b987bdfaf3a07029b03468affc2f2af2daa1013b3e5040d1bb9c5c43fef0 3.805432343000 1107363 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": 666270, "vin": [ { "gen": { "height": 666260 } } ], "vout": [ { "amount": 3805432343, "target": { "key": "5163b987bdfaf3a07029b03468affc2f2af2daa1013b3e5040d1bb9c5c43fef0" } } ], "extra": [ 1, 163, 231, 49, 111, 110, 109, 1, 221, 239, 215, 61, 9, 212, 230, 198, 213, 18, 164, 160, 5, 72, 197, 183, 37, 125, 244, 239, 207, 60, 116, 67, 155, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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