Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 944c1a0afc5802e2c8541ea2c342ae92c8f57bcca6d9fe348006f38eee403100

Tx prefix hash: 03dc15e7b14fcab2e58987639df3921b55d201dd0ff35b1d97885a1325b40931
Tx public key: 3e633aae6eb9cc33bb3659aeabfae39277d0f6b9479ceb4c4435d68e071a35a4
Timestamp: 1727280396 Timestamp [UCT]: 2024-09-25 16:06:36 Age [y:d:h:m:s]: 00:229:12:01:50
Block: 1117911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163859 RingCT/type: yes/0
Extra: 013e633aae6eb9cc33bb3659aeabfae39277d0f6b9479ceb4c4435d68e071a35a402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe74b3dd96f9c118e1d4689489ff64b714b3770e65239345a2855637b942d776 0.600000000000 1598918 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": 1117921, "vin": [ { "gen": { "height": 1117911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe74b3dd96f9c118e1d4689489ff64b714b3770e65239345a2855637b942d776" } } ], "extra": [ 1, 62, 99, 58, 174, 110, 185, 204, 51, 187, 54, 89, 174, 171, 250, 227, 146, 119, 208, 246, 185, 71, 156, 235, 76, 68, 53, 214, 142, 7, 26, 53, 164, 2, 17, 0, 0, 0, 3, 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