Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a31a6c096e721e0d6a95466ab291637d70526dbd8665cbb11d36c4a6553df6b

Tx prefix hash: f676d4acf13dbedb7a4db82e44b3adc910f67e17fe61df777109b8d69cd37d8a
Tx public key: 75c46d60f67b342e7fd6e79f23feb922c9354d04afd5faede9fee40ed273a0f3
Timestamp: 1680997259 Timestamp [UCT]: 2023-04-08 23:40:59 Age [y:d:h:m:s]: 02:046:14:00:20
Block: 734494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 555439 RingCT/type: yes/0
Extra: 0175c46d60f67b342e7fd6e79f23feb922c9354d04afd5faede9fee40ed273a0f302110000000333af99f4000000000000000000

1 output(s) for total of 2.261084021000 dcy

stealth address amount amount idx
00: 289086f2ddd2e1dd5adf98ab91cc6eb2daea206f0f37b5c80910b4936848d779 2.261084021000 1180709 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": 734504, "vin": [ { "gen": { "height": 734494 } } ], "vout": [ { "amount": 2261084021, "target": { "key": "289086f2ddd2e1dd5adf98ab91cc6eb2daea206f0f37b5c80910b4936848d779" } } ], "extra": [ 1, 117, 196, 109, 96, 246, 123, 52, 46, 127, 214, 231, 159, 35, 254, 185, 34, 201, 53, 77, 4, 175, 213, 250, 237, 233, 254, 228, 14, 210, 115, 160, 243, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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