Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9268c68ac71b13e46cfff87e214c5c8e2f026cf4cc128cb929761bfc1aa30d2d

Tx prefix hash: bba4b1be4a6e5d784b844a1cf3b23ade5ed92ce77ce4f51cb9193374b115abcc
Tx public key: 60144c83ab1377305a4fd53dded62939b8c48ce3e28b739d5f9087494ea037af
Timestamp: 1721728009 Timestamp [UCT]: 2024-07-23 09:46:49 Age [y:d:h:m:s]: 01:117:17:14:56
Block: 1071870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342656 RingCT/type: yes/0
Extra: 0160144c83ab1377305a4fd53dded62939b8c48ce3e28b739d5f9087494ea037af02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ee7f99a09a08153c2ad2d6fbfff179443f84c4cffdfdc1f9f3b871a40175a18 0.600000000000 1544259 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": 1071880, "vin": [ { "gen": { "height": 1071870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ee7f99a09a08153c2ad2d6fbfff179443f84c4cffdfdc1f9f3b871a40175a18" } } ], "extra": [ 1, 96, 20, 76, 131, 171, 19, 119, 48, 90, 79, 213, 61, 222, 214, 41, 57, 184, 196, 140, 227, 226, 139, 115, 157, 95, 144, 135, 73, 78, 160, 55, 175, 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