Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7723bb8ce61d2c33db6e3c592232c42ee64a279e17a71d1c87aac85b5da063d

Tx prefix hash: 3cce7891303c85d8e25716436ae0a6ac6b1b1796f4dd89eb04f4747c70f62e04
Tx public key: 9dc021510a16544788c6c2bfe26d0828f6135bdc9d338aa6e067d1cfc5957dcc
Timestamp: 1747745225 Timestamp [UCT]: 2025-05-20 12:47:05 Age [y:d:h:m:s]: 00:233:19:07:49
Block: 1287044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164864 RingCT/type: yes/0
Extra: 019dc021510a16544788c6c2bfe26d0828f6135bdc9d338aa6e067d1cfc5957dcc0211000000051f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65b2fe7889cc91c310a578966fc2917d8118f040f0cdbdea6ee66e2d77b90506 0.600000000000 1774511 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": 1287054, "vin": [ { "gen": { "height": 1287044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65b2fe7889cc91c310a578966fc2917d8118f040f0cdbdea6ee66e2d77b90506" } } ], "extra": [ 1, 157, 192, 33, 81, 10, 22, 84, 71, 136, 198, 194, 191, 226, 109, 8, 40, 246, 19, 91, 220, 157, 51, 138, 166, 224, 103, 209, 207, 197, 149, 125, 204, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 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