Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e3c5e6c85bc20a27f3bb417dc22f05f9e8bb3a1823446c9718e620edc683785

Tx prefix hash: f41b1053348e782792c9d496f103b26c10ff8279fd8fd6234e910efdb738b2b8
Tx public key: b82f27d49d42240e70047690ddb8aa70a88de1821e94a20a5210b3a7a822d35f
Timestamp: 1738307273 Timestamp [UCT]: 2025-01-31 07:07:53 Age [y:d:h:m:s]: 00:293:10:36:32
Block: 1208913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207476 RingCT/type: yes/0
Extra: 01b82f27d49d42240e70047690ddb8aa70a88de1821e94a20a5210b3a7a822d35f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cd8e4fad9e170ac2ef784da97a78f1af5fa8ae8d469f29432aa532951841260 0.600000000000 1695650 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": 1208923, "vin": [ { "gen": { "height": 1208913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cd8e4fad9e170ac2ef784da97a78f1af5fa8ae8d469f29432aa532951841260" } } ], "extra": [ 1, 184, 47, 39, 212, 157, 66, 36, 14, 112, 4, 118, 144, 221, 184, 170, 112, 168, 141, 225, 130, 30, 148, 162, 10, 82, 16, 179, 167, 168, 34, 211, 95, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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