Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ad3704efa59f1d88961a5869fbe577f9aead47fbebcd433d2b07618840c9152

Tx prefix hash: 7bc35285d8661539e3deb5bbb431126ecac13716f255c578f16958a7bebb3a29
Tx public key: e16dbbe76587525f4c912f14f08a903cb9c0a9a5b36efb1840a0d0e9138ccd38
Timestamp: 1711485301 Timestamp [UCT]: 2024-03-26 20:35:01 Age [y:d:h:m:s]: 00:294:06:22:29
Block: 986994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210608 RingCT/type: yes/0
Extra: 01e16dbbe76587525f4c912f14f08a903cb9c0a9a5b36efb1840a0d0e9138ccd3802110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d81ae83f2f70293dc727a4a099e9f7351597e43c36006e008b62f9a68b330d76 0.600000000000 1447233 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": 987004, "vin": [ { "gen": { "height": 986994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d81ae83f2f70293dc727a4a099e9f7351597e43c36006e008b62f9a68b330d76" } } ], "extra": [ 1, 225, 109, 187, 231, 101, 135, 82, 95, 76, 145, 47, 20, 240, 138, 144, 60, 185, 192, 169, 165, 179, 110, 251, 24, 64, 160, 208, 233, 19, 140, 205, 56, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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