Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1ffb9bcdbd40979c2f4bbf74da286db5d814d2ca653b463c6c20129481a85cc

Tx prefix hash: f6b154ffac1439e325e2df31b536143c9679124daa9ee68c9792da58c82f781f
Tx public key: 60fa2babbbafdd94da3dcb020fbcd635710d666a6adb6c57e7d0a239aea4c7a0
Timestamp: 1725254326 Timestamp [UCT]: 2024-09-02 05:18:46 Age [y:d:h:m:s]: 00:083:14:31:57
Block: 1101121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59789 RingCT/type: yes/0
Extra: 0160fa2babbbafdd94da3dcb020fbcd635710d666a6adb6c57e7d0a239aea4c7a002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48ca82534ceefd3d7a708609bd96936ecc416d4da94ddf8443d3c1e380a5c399 0.600000000000 1577102 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": 1101131, "vin": [ { "gen": { "height": 1101121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48ca82534ceefd3d7a708609bd96936ecc416d4da94ddf8443d3c1e380a5c399" } } ], "extra": [ 1, 96, 250, 43, 171, 187, 175, 221, 148, 218, 61, 203, 2, 15, 188, 214, 53, 113, 13, 102, 106, 106, 219, 108, 87, 231, 208, 162, 57, 174, 164, 199, 160, 2, 17, 0, 0, 0, 5, 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