Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71d9e37f200f9c6fbc7f7a2511dfb2fa03cc5b80fb3f6904b105c10d9c108338

Tx prefix hash: 442f16b55199bfa09f9a632711b2b16f77b290cca0eb3f8b7c374807e28a887d
Tx public key: 5f70c46e3008863d7bf8bdc369ac70f4535b3deb3250b415dfc075aa76c8b3c8
Timestamp: 1737655202 Timestamp [UCT]: 2025-01-23 18:00:02 Age [y:d:h:m:s]: 00:147:05:20:46
Block: 1203725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104945 RingCT/type: yes/0
Extra: 015f70c46e3008863d7bf8bdc369ac70f4535b3deb3250b415dfc075aa76c8b3c80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34c71518185855872956ab0be3db31eb76ecfca55bed824ff25a20770632f4e1 0.600000000000 1690404 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": 1203735, "vin": [ { "gen": { "height": 1203725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34c71518185855872956ab0be3db31eb76ecfca55bed824ff25a20770632f4e1" } } ], "extra": [ 1, 95, 112, 196, 110, 48, 8, 134, 61, 123, 248, 189, 195, 105, 172, 112, 244, 83, 91, 61, 235, 50, 80, 180, 21, 223, 192, 117, 170, 118, 200, 179, 200, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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