Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7271eaff7143cbf3ba6a731d3f5e40841d7260f40df55328e33be5657cd7c458

Tx prefix hash: f5a9cdc70fae6d2f34c8fb1fff27aadf6eb02155d028a7d62573e6a97226fbfa
Tx public key: 977dac7640fefd74fc241470d4181c418b08c25c5af963cada526f0181eeb05a
Timestamp: 1745714994 Timestamp [UCT]: 2025-04-27 00:49:54 Age [y:d:h:m:s]: 00:208:07:57:18
Block: 1270227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146601 RingCT/type: yes/0
Extra: 01977dac7640fefd74fc241470d4181c418b08c25c5af963cada526f0181eeb05a0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da6ffb6b0ea4ece17f5a262c2c6a12990e2d5422724b9d6965ce39b8abe912bd 0.600000000000 1757468 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": 1270237, "vin": [ { "gen": { "height": 1270227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da6ffb6b0ea4ece17f5a262c2c6a12990e2d5422724b9d6965ce39b8abe912bd" } } ], "extra": [ 1, 151, 125, 172, 118, 64, 254, 253, 116, 252, 36, 20, 112, 212, 24, 28, 65, 139, 8, 194, 92, 90, 249, 99, 202, 218, 82, 111, 1, 129, 238, 176, 90, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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