Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c98615afdf0f9e7c6a6d8f5348f505993e71c84c69e4303c58af062ccdcd6c4

Tx prefix hash: 247357f33b38041fa070d54533934abbecbd8606c7b0b60540df651ce0e9e643
Tx public key: cf9fe08e374ba5830759402c24e3e04ff6dc8557c03c3a29e045e778decddba2
Timestamp: 1648225048 Timestamp [UCT]: 2022-03-25 16:17:28 Age [y:d:h:m:s]: 02:238:22:34:01
Block: 466200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 690253 RingCT/type: yes/0
Extra: 01cf9fe08e374ba5830759402c24e3e04ff6dc8557c03c3a29e045e778decddba2021100000007a272b9cb000000000000000000

1 output(s) for total of 17.509999199000 dcy

stealth address amount amount idx
00: 1cc3c3be440f5b74df163694624bc1096c43cd64f26dfee86fc403f1c15fa50a 17.509999199000 884471 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": 466210, "vin": [ { "gen": { "height": 466200 } } ], "vout": [ { "amount": 17509999199, "target": { "key": "1cc3c3be440f5b74df163694624bc1096c43cd64f26dfee86fc403f1c15fa50a" } } ], "extra": [ 1, 207, 159, 224, 142, 55, 75, 165, 131, 7, 89, 64, 44, 36, 227, 224, 79, 246, 220, 133, 87, 192, 60, 58, 41, 224, 69, 231, 120, 222, 205, 219, 162, 2, 17, 0, 0, 0, 7, 162, 114, 185, 203, 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