Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c17b573a60dc6b21ed05a8d2d4005d65d889db7d517561ebb49df97d4bbb98f

Tx prefix hash: d675bbfd42c4ceaf80ccc5d2eb1b067117587329668b102b2f7fc6eed23f9b63
Tx public key: 3cdb594c6de2228579b6e5610a0ffe45326f4d4affd088c78c2969a7a47409aa
Timestamp: 1676898598 Timestamp [UCT]: 2023-02-20 13:09:58 Age [y:d:h:m:s]: 02:098:13:55:27
Block: 701101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592099 RingCT/type: yes/0
Extra: 013cdb594c6de2228579b6e5610a0ffe45326f4d4affd088c78c2969a7a47409aa02110000000374b6d784000000000000000000

1 output(s) for total of 2.917166770000 dcy

stealth address amount amount idx
00: 41a40e399583778df46a218a580eef874a54b856129febfb238ad69fe4d086c7 2.917166770000 1144564 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": 701111, "vin": [ { "gen": { "height": 701101 } } ], "vout": [ { "amount": 2917166770, "target": { "key": "41a40e399583778df46a218a580eef874a54b856129febfb238ad69fe4d086c7" } } ], "extra": [ 1, 60, 219, 89, 76, 109, 226, 34, 133, 121, 182, 229, 97, 10, 15, 254, 69, 50, 111, 77, 74, 255, 208, 136, 199, 140, 41, 105, 167, 164, 116, 9, 170, 2, 17, 0, 0, 0, 3, 116, 182, 215, 132, 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