Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b8afb393c27e71744c2674cb0eff3e918ce973c57da1720724962a1f3d814d4

Tx prefix hash: 9057c70c6a9906b2a288ef039f69b6247d8b66a3f115e3f122a1d23f23e4b62a
Tx public key: 97a52eae9c5872848d0ea3855f61b9cceb3cfc6f506930bf3291967c40750016
Timestamp: 1736745320 Timestamp [UCT]: 2025-01-13 05:15:20 Age [y:d:h:m:s]: 00:310:14:29:08
Block: 1196237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219501 RingCT/type: yes/0
Extra: 0197a52eae9c5872848d0ea3855f61b9cceb3cfc6f506930bf3291967c40750016021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68a85df3d71c5286edff8f3f54143a490e4bdaa7e8bf3e0d6edaccabe88817d1 0.600000000000 1682834 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": 1196247, "vin": [ { "gen": { "height": 1196237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68a85df3d71c5286edff8f3f54143a490e4bdaa7e8bf3e0d6edaccabe88817d1" } } ], "extra": [ 1, 151, 165, 46, 174, 156, 88, 114, 132, 141, 14, 163, 133, 95, 97, 185, 204, 235, 60, 252, 111, 80, 105, 48, 191, 50, 145, 150, 124, 64, 117, 0, 22, 2, 17, 0, 0, 0, 4, 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