Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebe494137c1629b04543c875b4a20b1d6c3507285f6ea19efe12c97516d2ee3c

Tx prefix hash: eecbc96a27596f6e12a4f92db42bbffde2e48838f0ebae19c1beebd9a7d815f8
Tx public key: 3592006ac6b14d686cbc28721316b3d118910f476de5cd41423d258ed86879dd
Timestamp: 1710695292 Timestamp [UCT]: 2024-03-17 17:08:12 Age [y:d:h:m:s]: 01:000:13:30:11
Block: 980433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261364 RingCT/type: yes/0
Extra: 013592006ac6b14d686cbc28721316b3d118910f476de5cd41423d258ed86879dd021100000002a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf38f3ca3140101f7cb91fb2975dd1fa7be37ecfcf93b074421b520dd7c1c0ae 0.600000000000 1440500 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": 980443, "vin": [ { "gen": { "height": 980433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf38f3ca3140101f7cb91fb2975dd1fa7be37ecfcf93b074421b520dd7c1c0ae" } } ], "extra": [ 1, 53, 146, 0, 106, 198, 177, 77, 104, 108, 188, 40, 114, 19, 22, 179, 209, 24, 145, 15, 71, 109, 229, 205, 65, 66, 61, 37, 142, 216, 104, 121, 221, 2, 17, 0, 0, 0, 2, 165, 223, 157, 134, 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