Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd8b8b0eb4ced5e53014b958efca5f70b49cd5d31755d7bb423af6d902cb9bfc

Tx prefix hash: d07e6c5a40a1086a5497c8439f576cbc8bea244d43fc0985850115bb01efcf1a
Tx public key: c16c0a6908f2a808034446b38e70e8ee4b027c3b742dce9bb0a4f069ffb6524e
Timestamp: 1735992889 Timestamp [UCT]: 2025-01-04 12:14:49 Age [y:d:h:m:s]: 00:087:09:03:49
Block: 1190013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62214 RingCT/type: yes/0
Extra: 01c16c0a6908f2a808034446b38e70e8ee4b027c3b742dce9bb0a4f069ffb6524e02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09887b61c4cf3eecd2933a7f054d4e046147c350f6dfd7e74f1e789d37f327ad 0.600000000000 1676528 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": 1190023, "vin": [ { "gen": { "height": 1190013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09887b61c4cf3eecd2933a7f054d4e046147c350f6dfd7e74f1e789d37f327ad" } } ], "extra": [ 1, 193, 108, 10, 105, 8, 242, 168, 8, 3, 68, 70, 179, 142, 112, 232, 238, 75, 2, 124, 59, 116, 45, 206, 155, 176, 164, 240, 105, 255, 182, 82, 78, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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