Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07a22dc2ff95d1ff9ba81a336abb0a8076a1ef6b34395eb9f52878902d5f6b97

Tx prefix hash: 6b521f7659effba9f545bdf776ad98e10ba02a6001779ad72abecb40da8f1211
Tx public key: d7e5f88c8810afadcb3fbe815c1d894748a23b1194ece42f1c651789c1adcfb1
Timestamp: 1723763435 Timestamp [UCT]: 2024-08-15 23:10:35 Age [y:d:h:m:s]: 00:237:21:29:55
Block: 1088758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169897 RingCT/type: yes/0
Extra: 01d7e5f88c8810afadcb3fbe815c1d894748a23b1194ece42f1c651789c1adcfb102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c703899be412871060e5d528c833a28812ecaa3ade9da5416b5a999959d2eb1 0.600000000000 1563377 of 15

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": 1088768, "vin": [ { "gen": { "height": 1088758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c703899be412871060e5d528c833a28812ecaa3ade9da5416b5a999959d2eb1" } } ], "extra": [ 1, 215, 229, 248, 140, 136, 16, 175, 173, 203, 63, 190, 129, 92, 29, 137, 71, 72, 162, 59, 17, 148, 236, 228, 47, 28, 101, 23, 137, 193, 173, 207, 177, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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