Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6e2123a19bf1300200cb7c1f200276550e44b6d66e8f7176d9941818ba7ab1d

Tx prefix hash: 54fc69b6f4642c9df0ed18e8cf5cbf786bf0e0b9e45ad6a24d3ca2f40b67093d
Tx public key: fc17b3ab8d5b1ed30558dafd1178184f397260e57765be5cda90fbfbb3a85a8d
Timestamp: 1634924631 Timestamp [UCT]: 2021-10-22 17:43:51 Age [y:d:h:m:s]: 04:013:16:19:17
Block: 358255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1046456 RingCT/type: yes/0
Extra: 01fc17b3ab8d5b1ed30558dafd1178184f397260e57765be5cda90fbfbb3a85a8d02110000000337cb3088000000000000000000

1 output(s) for total of 39.898160934000 dcy

stealth address amount amount idx
00: 9779fba4647a2d006c23784fc8e9779e3365cf15f636dfa32b82244ba5cc8c6e 39.898160934000 730078 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": 358265, "vin": [ { "gen": { "height": 358255 } } ], "vout": [ { "amount": 39898160934, "target": { "key": "9779fba4647a2d006c23784fc8e9779e3365cf15f636dfa32b82244ba5cc8c6e" } } ], "extra": [ 1, 252, 23, 179, 171, 141, 91, 30, 211, 5, 88, 218, 253, 17, 120, 24, 79, 57, 114, 96, 229, 119, 101, 190, 92, 218, 144, 251, 251, 179, 168, 90, 141, 2, 17, 0, 0, 0, 3, 55, 203, 48, 136, 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