Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bb212b9c532d8e36ba87dd95ea2f58f22038c5ff66a1a6b4e78d0f94598df48

Tx prefix hash: 54b83a58c2301e1dff1ec511fbb35a60bc19417db20baa0b7432c52f8c3c33f9
Tx public key: bb454a0cb0530cfa2ef21d83a00c417ced011daab735cfcc84f652513923dda6
Timestamp: 1699343675 Timestamp [UCT]: 2023-11-07 07:54:35 Age [y:d:h:m:s]: 01:336:14:48:39
Block: 886310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499438 RingCT/type: yes/0
Extra: 01bb454a0cb0530cfa2ef21d83a00c417ced011daab735cfcc84f652513923dda6021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.710046921000 dcy

stealth address amount amount idx
00: 8f12cd279aac1030f5da8d71f528f7c50f0c1be8957c4191a463c9845261a681 0.710046921000 1342123 of 0

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": 886320, "vin": [ { "gen": { "height": 886310 } } ], "vout": [ { "amount": 710046921, "target": { "key": "8f12cd279aac1030f5da8d71f528f7c50f0c1be8957c4191a463c9845261a681" } } ], "extra": [ 1, 187, 69, 74, 12, 176, 83, 12, 250, 46, 242, 29, 131, 160, 12, 65, 124, 237, 1, 29, 170, 183, 53, 207, 204, 132, 246, 82, 81, 57, 35, 221, 166, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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