Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12b7187eaa7b9e4f2708b0c69d459f4bcaa230fc748044f386b8e4a2baeae164

Tx prefix hash: 669a4fc80947e00feb7e4eedc1423a4f0aceefe88e1665db3626be01c5dea5a6
Tx public key: d7c6c545caf6c4c8326b96bdd5388315351c17605a05152c39796a71fc9ff966
Timestamp: 1745162994 Timestamp [UCT]: 2025-04-20 15:29:54 Age [y:d:h:m:s]: 00:023:22:47:39
Block: 1265648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17152 RingCT/type: yes/0
Extra: 01d7c6c545caf6c4c8326b96bdd5388315351c17605a05152c39796a71fc9ff966021100000002dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40813ac46705630b33db19ea6f28b4cff961ceccdc814f4691b347e4105e1d10 0.600000000000 1752861 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": 1265658, "vin": [ { "gen": { "height": 1265648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40813ac46705630b33db19ea6f28b4cff961ceccdc814f4691b347e4105e1d10" } } ], "extra": [ 1, 215, 198, 197, 69, 202, 246, 196, 200, 50, 107, 150, 189, 213, 56, 131, 21, 53, 28, 23, 96, 90, 5, 21, 44, 57, 121, 106, 113, 252, 159, 249, 102, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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