Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47bd97bc0d86c860e3fe8e92246604e2659a8b41f0791f675cfc2e8286c88e73

Tx prefix hash: 02da2bba1c826c4bada5ed1cfd8643f3ee4ea927471848837de810825bf68b87
Tx public key: dcca60ac931c7d0c1c8eea69bec5f3d833a45d61c2e7ef0669fb84674185b6c3
Timestamp: 1705465377 Timestamp [UCT]: 2024-01-17 04:22:57 Age [y:d:h:m:s]: 01:142:03:36:45
Block: 937027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362752 RingCT/type: yes/0
Extra: 01dcca60ac931c7d0c1c8eea69bec5f3d833a45d61c2e7ef0669fb84674185b6c302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd22c6692b951f4bd80d85f424766c2f9fd5cd49d1099459b1c01a3c9a6bef9c 0.600000000000 1395071 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": 937037, "vin": [ { "gen": { "height": 937027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd22c6692b951f4bd80d85f424766c2f9fd5cd49d1099459b1c01a3c9a6bef9c" } } ], "extra": [ 1, 220, 202, 96, 172, 147, 28, 125, 12, 28, 142, 234, 105, 190, 197, 243, 216, 51, 164, 93, 97, 194, 231, 239, 6, 105, 251, 132, 103, 65, 133, 182, 195, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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