Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e3d42cf2452d6917f84b4072ed5bd27eaa177c2b4f1c589118385e711d345fe

Tx prefix hash: 37df5326e5d9c1ff9e0a110e367f9635cb9bc41084a37c8078b7a71e88cb7e2b
Tx public key: 7035d6d6c606f4f6311f472e79a81438514157ce5c12a8b63ddd2541e850d1a5
Timestamp: 1736521634 Timestamp [UCT]: 2025-01-10 15:07:14 Age [y:d:h:m:s]: 00:148:13:07:34
Block: 1194384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105992 RingCT/type: yes/0
Extra: 017035d6d6c606f4f6311f472e79a81438514157ce5c12a8b63ddd2541e850d1a50211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95b1b9008966361395d203aeeb00b17217c60c514a73ea0ab557f5ac131fc78e 0.600000000000 1680955 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": 1194394, "vin": [ { "gen": { "height": 1194384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95b1b9008966361395d203aeeb00b17217c60c514a73ea0ab557f5ac131fc78e" } } ], "extra": [ 1, 112, 53, 214, 214, 198, 6, 244, 246, 49, 31, 71, 46, 121, 168, 20, 56, 81, 65, 87, 206, 92, 18, 168, 182, 61, 221, 37, 65, 232, 80, 209, 165, 2, 17, 0, 0, 0, 9, 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