Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edd303446d52968f22650618d8a2a224141b17d24736f40f8237338bfd93d7dd

Tx prefix hash: 307a8f0b8deff506c36d759bdd1b804188f57383f8d15b94d6eef2e6e38d7eec
Tx public key: 7086468d419692e7a3dbbf10b750080dddd5e5d2c9f52c96710cb9817489ad3e
Timestamp: 1625558828 Timestamp [UCT]: 2021-07-06 08:07:08 Age [y:d:h:m:s]: 03:218:16:10:09
Block: 289059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 926085 RingCT/type: yes/0
Extra: 017086468d419692e7a3dbbf10b750080dddd5e5d2c9f52c96710cb9817489ad3e0211000000149c1fbdcc000000000000000000

1 output(s) for total of 67.648797572000 dcy

stealth address amount amount idx
00: 684171cc0da0b201fd234f934b2006339bbe531883f39e8d58673418a784be79 67.648797572000 605460 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": 289069, "vin": [ { "gen": { "height": 289059 } } ], "vout": [ { "amount": 67648797572, "target": { "key": "684171cc0da0b201fd234f934b2006339bbe531883f39e8d58673418a784be79" } } ], "extra": [ 1, 112, 134, 70, 141, 65, 150, 146, 231, 163, 219, 191, 16, 183, 80, 8, 13, 221, 213, 229, 210, 201, 245, 44, 150, 113, 12, 185, 129, 116, 137, 173, 62, 2, 17, 0, 0, 0, 20, 156, 31, 189, 204, 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