Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34ee08147070fa6cfaf1bba1deeadab4f0804f1b4504b5064b0e762e8178d8f1

Tx prefix hash: 744fedb43ed6f748be3a70a2bd23bb2c86371a46a8328b59da4564fcedc09c1a
Tx public key: 69bd02304f919dbebe0f07162f037fe1ef272f273142b3f78b3276ff3a8d0069
Timestamp: 1719371343 Timestamp [UCT]: 2024-06-26 03:09:03 Age [y:d:h:m:s]: 00:320:19:33:40
Block: 1052333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229270 RingCT/type: yes/0
Extra: 0169bd02304f919dbebe0f07162f037fe1ef272f273142b3f78b3276ff3a8d00690211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43560e64cb30f3a38a6d794c7cd70d8c93e28d18817ff9c1abc6e26659f728de 0.600000000000 1522656 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": 1052343, "vin": [ { "gen": { "height": 1052333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43560e64cb30f3a38a6d794c7cd70d8c93e28d18817ff9c1abc6e26659f728de" } } ], "extra": [ 1, 105, 189, 2, 48, 79, 145, 157, 190, 190, 15, 7, 22, 47, 3, 127, 225, 239, 39, 47, 39, 49, 66, 179, 247, 139, 50, 118, 255, 58, 141, 0, 105, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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