Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1a5a1ac4a643ea5bb18961993d71e9892d929ebf6f7a5c969e2fccb6ff3111c

Tx prefix hash: 0210583eee048df576c4ea4164edb2c849c879b14df539586d00f1eccfa4ece6
Tx public key: 7d4d029e8e9103c110777cb7a72d965891427a31f0db041b1cacf3523bf65eeb
Timestamp: 1743987099 Timestamp [UCT]: 2025-04-07 00:51:39 Age [y:d:h:m:s]: 00:276:23:05:32
Block: 1255913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195760 RingCT/type: yes/0
Extra: 017d4d029e8e9103c110777cb7a72d965891427a31f0db041b1cacf3523bf65eeb0211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 998abd0c9077986573f423f5d65a150ce44396be8dab9392b4b557c9533cec46 0.600000000000 1743020 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": 1255923, "vin": [ { "gen": { "height": 1255913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "998abd0c9077986573f423f5d65a150ce44396be8dab9392b4b557c9533cec46" } } ], "extra": [ 1, 125, 77, 2, 158, 142, 145, 3, 193, 16, 119, 124, 183, 167, 45, 150, 88, 145, 66, 122, 49, 240, 219, 4, 27, 28, 172, 243, 82, 59, 246, 94, 235, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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