Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 373c119256006d873076ca88033024a9e25b9305b3d72242179f568e97c7ef91

Tx prefix hash: 3fb64688ea7ceb025810ef5ea2195689b6ea315bea4b71a35989a4d5b34b9c29
Tx public key: f8a1deb3667b7132d0a4c6b26bcffb5e3935bfbdacbe01bcf20fca756840f0dc
Timestamp: 1721167753 Timestamp [UCT]: 2024-07-16 22:09:13 Age [y:d:h:m:s]: 00:257:13:19:42
Block: 1067254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183982 RingCT/type: yes/0
Extra: 01f8a1deb3667b7132d0a4c6b26bcffb5e3935bfbdacbe01bcf20fca756840f0dc02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1798d9f40a27f6ba2e8a1a5ef608379704ab6a9db9db3b56677ec64e93baceb6 0.600000000000 1538017 of 15

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": 1067264, "vin": [ { "gen": { "height": 1067254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1798d9f40a27f6ba2e8a1a5ef608379704ab6a9db9db3b56677ec64e93baceb6" } } ], "extra": [ 1, 248, 161, 222, 179, 102, 123, 113, 50, 208, 164, 198, 178, 107, 207, 251, 94, 57, 53, 191, 189, 172, 190, 1, 188, 242, 15, 202, 117, 104, 64, 240, 220, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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