Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 646469558c7dcb983fd7866615027917692b51d0fe71c3f121e4faecb6059dcf

Tx prefix hash: dc7840c53d5c0d9bd408c674c4044dcbf9ca8af422c45b5c944c962612ee3da3
Tx public key: ce9f80cbd6350b5ea1d3e47954c9a572c8c1a48c213c5b2c72f5f25e9352257c
Timestamp: 1577521124 Timestamp [UCT]: 2019-12-28 08:18:44 Age [y:d:h:m:s]: 05:001:05:13:02
Block: 33276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151046 RingCT/type: yes/0
Extra: 01ce9f80cbd6350b5ea1d3e47954c9a572c8c1a48c213c5b2c72f5f25e9352257c02110000000ead433a0b000000000000000000

1 output(s) for total of 476.149854505000 dcy

stealth address amount amount idx
00: 833a49cc8ffed9d8dcf7f759d49e390097cbc7ba48cb18a0df166ed7ce124cb5 476.149854505000 55683 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": 33286, "vin": [ { "gen": { "height": 33276 } } ], "vout": [ { "amount": 476149854505, "target": { "key": "833a49cc8ffed9d8dcf7f759d49e390097cbc7ba48cb18a0df166ed7ce124cb5" } } ], "extra": [ 1, 206, 159, 128, 203, 214, 53, 11, 94, 161, 211, 228, 121, 84, 201, 165, 114, 200, 193, 164, 140, 33, 60, 91, 44, 114, 245, 242, 94, 147, 82, 37, 124, 2, 17, 0, 0, 0, 14, 173, 67, 58, 11, 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