Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c1912e1fa6642f7cf58843d1562afcaeaedaff2a1f93a851113bd5956719fa2

Tx prefix hash: 2f7616236fef47c3a4d272f6f685bc527e94648b1e35672bf28ea7c97d76e884
Tx public key: 06b6408df48b55a0364f51e52794c4b51b976008d6f4fb87a80d219d6f078d31
Timestamp: 1577191474 Timestamp [UCT]: 2019-12-24 12:44:34 Age [y:d:h:m:s]: 05:044:19:02:14
Block: 30699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181800 RingCT/type: yes/0
Extra: 0106b6408df48b55a0364f51e52794c4b51b976008d6f4fb87a80d219d6f078d3102110000003ee39b962a000000000000000000

1 output(s) for total of 485.604083931000 dcy

stealth address amount amount idx
00: 8f8a618c6fee22d50e84e3d20bdf31d5e99e012b879faf8465c9ffbc03f6856e 485.604083931000 50687 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": 30709, "vin": [ { "gen": { "height": 30699 } } ], "vout": [ { "amount": 485604083931, "target": { "key": "8f8a618c6fee22d50e84e3d20bdf31d5e99e012b879faf8465c9ffbc03f6856e" } } ], "extra": [ 1, 6, 182, 64, 141, 244, 139, 85, 160, 54, 79, 81, 229, 39, 148, 196, 181, 27, 151, 96, 8, 214, 244, 251, 135, 168, 13, 33, 157, 111, 7, 141, 49, 2, 17, 0, 0, 0, 62, 227, 155, 150, 42, 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