Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 186aef74fded091f71da3faedba671a1781102a48f4471a42778e608082d33b6

Tx prefix hash: 6c68b240d263c7f16e0d216c0dc7a845265b192d1b7aff6cd48a014569d8cb35
Tx public key: 15403a96b00fb19b54ad990aef1c4de5fd69249b68aea687d2268fbe81360dc7
Timestamp: 1702038351 Timestamp [UCT]: 2023-12-08 12:25:51 Age [y:d:h:m:s]: 01:109:15:34:32
Block: 908635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339496 RingCT/type: yes/0
Extra: 0115403a96b00fb19b54ad990aef1c4de5fd69249b68aea687d2268fbe81360dc702110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6a77061825b27f0e65aa8c43d683a2c6d184fa972156713fe930ac4234c91eb 0.600000000000 1365680 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": 908645, "vin": [ { "gen": { "height": 908635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6a77061825b27f0e65aa8c43d683a2c6d184fa972156713fe930ac4234c91eb" } } ], "extra": [ 1, 21, 64, 58, 150, 176, 15, 177, 155, 84, 173, 153, 10, 239, 28, 77, 229, 253, 105, 36, 155, 104, 174, 166, 135, 210, 38, 143, 190, 129, 54, 13, 199, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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