Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ccdd415a3ce0f5d4e064cffe953d6a090216cb61b692d269c73eb0eacfec2a8

Tx prefix hash: b6d4cde203f823698f0287bf1a130f5ca99d4e802961c6beb6238775ad48ae05
Tx public key: 1c96c0755ede07f3f3c90ffe714b0ba5a1c0267de604f85e2c9525ad4e9ba8bc
Timestamp: 1635290951 Timestamp [UCT]: 2021-10-26 23:29:11 Age [y:d:h:m:s]: 03:184:03:59:59
Block: 361165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 909863 RingCT/type: yes/0
Extra: 011c96c0755ede07f3f3c90ffe714b0ba5a1c0267de604f85e2c9525ad4e9ba8bc021100000015328bb496000000000000000000

1 output(s) for total of 39.022117789000 dcy

stealth address amount amount idx
00: d281ce470826f09280a92df1c38b6f4d00e1a3c88f9905073fafd34e1aff4337 39.022117789000 734890 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": 361175, "vin": [ { "gen": { "height": 361165 } } ], "vout": [ { "amount": 39022117789, "target": { "key": "d281ce470826f09280a92df1c38b6f4d00e1a3c88f9905073fafd34e1aff4337" } } ], "extra": [ 1, 28, 150, 192, 117, 94, 222, 7, 243, 243, 201, 15, 254, 113, 75, 11, 165, 161, 192, 38, 125, 230, 4, 248, 94, 44, 149, 37, 173, 78, 155, 168, 188, 2, 17, 0, 0, 0, 21, 50, 139, 180, 150, 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