Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfa1ae07fe28111216405dae7ae58f6f7dcf8082ef39130a8d3d8b978d23cd0f

Tx prefix hash: 30ecc949ec3d6402d4dbd537ffea47eaac7fe85e827eca983aa605f0727628a1
Tx public key: e3ccb5da61451746ad2691e89a320e185d2fdc12b26aa0ac0c91f617ca89b006
Timestamp: 1743459866 Timestamp [UCT]: 2025-03-31 22:24:26 Age [y:d:h:m:s]: 00:234:03:07:56
Block: 1251556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165060 RingCT/type: yes/0
Extra: 01e3ccb5da61451746ad2691e89a320e185d2fdc12b26aa0ac0c91f617ca89b006021100000004a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb0850cdf28e21b0fe683cbe2e6b43ad6c97d76262c3a3d6298a72774a190244 0.600000000000 1738625 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": 1251566, "vin": [ { "gen": { "height": 1251556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb0850cdf28e21b0fe683cbe2e6b43ad6c97d76262c3a3d6298a72774a190244" } } ], "extra": [ 1, 227, 204, 181, 218, 97, 69, 23, 70, 173, 38, 145, 232, 154, 50, 14, 24, 93, 47, 220, 18, 178, 106, 160, 172, 12, 145, 246, 23, 202, 137, 176, 6, 2, 17, 0, 0, 0, 4, 162, 237, 1, 107, 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