Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 522c8f59e29c4b061b058016327c5771e41b71a59a1545cb74fc8ad4da054729

Tx prefix hash: d88ea764c973a25b51317d388a160e09b9711ca4f4e83a9a6940e8cbeaecacdd
Tx public key: 0f3317b038b782c963bb20052e57140279974f4f61df3392213824e849148822
Timestamp: 1625630341 Timestamp [UCT]: 2021-07-07 03:59:01 Age [y:d:h:m:s]: 03:322:20:25:01
Block: 289466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1000790 RingCT/type: yes/0
Extra: 010f3317b038b782c963bb20052e57140279974f4f61df3392213824e849148822021100000005ed79a617000000000000000000

1 output(s) for total of 67.434087461000 dcy

stealth address amount amount idx
00: 648845bda9d1f882a3d07f2c464f89d7682cc11b85eaead238a4ba9a76cfd91d 67.434087461000 606264 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": 289476, "vin": [ { "gen": { "height": 289466 } } ], "vout": [ { "amount": 67434087461, "target": { "key": "648845bda9d1f882a3d07f2c464f89d7682cc11b85eaead238a4ba9a76cfd91d" } } ], "extra": [ 1, 15, 51, 23, 176, 56, 183, 130, 201, 99, 187, 32, 5, 46, 87, 20, 2, 121, 151, 79, 79, 97, 223, 51, 146, 33, 56, 36, 232, 73, 20, 136, 34, 2, 17, 0, 0, 0, 5, 237, 121, 166, 23, 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