Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46c9ec10a73a74c29105533c2287c26cf5568873ede73067ea5c6e843b3cc789

Tx prefix hash: 9b09d48e964228708976cae65ade58845d9e0a597a0eedc203d10a34d901f23b
Tx public key: e9c99fcd3d31c8a6cb4d67f6c9cffdd21864fbcb1d7cb1442bc2be7bb467379a
Timestamp: 1723233429 Timestamp [UCT]: 2024-08-09 19:57:09 Age [y:d:h:m:s]: 00:135:08:48:18
Block: 1084360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96875 RingCT/type: yes/0
Extra: 01e9c99fcd3d31c8a6cb4d67f6c9cffdd21864fbcb1d7cb1442bc2be7bb467379a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01b2132986898a0f043034f80b528267eb25d3db33d93022ec397fa51c6663c4 0.600000000000 1558609 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": 1084370, "vin": [ { "gen": { "height": 1084360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01b2132986898a0f043034f80b528267eb25d3db33d93022ec397fa51c6663c4" } } ], "extra": [ 1, 233, 201, 159, 205, 61, 49, 200, 166, 203, 77, 103, 246, 201, 207, 253, 210, 24, 100, 251, 203, 29, 124, 177, 68, 43, 194, 190, 123, 180, 103, 55, 154, 2, 17, 0, 0, 0, 4, 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