Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90e9453940d10e4c228ec8da65ff51db4bc83cd333907be6e88cf683b9fe82ca

Tx prefix hash: 2ac20e130a35a3d00c1bebbe77a53cd1fc895b1bef965234c9cd28df6d3a0f8a
Tx public key: 0ce10b1de9ac77b1fc76cefc7fd8d953bd2576eda571ec7c2464c8afb8a75adf
Timestamp: 1736126280 Timestamp [UCT]: 2025-01-06 01:18:00 Age [y:d:h:m:s]: 00:084:17:12:25
Block: 1191119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60323 RingCT/type: yes/0
Extra: 010ce10b1de9ac77b1fc76cefc7fd8d953bd2576eda571ec7c2464c8afb8a75adf0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 790feb4019102515386d80948a54e36906865d74e92caa2e3baf325c3c4fd8ae 0.600000000000 1677642 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": 1191129, "vin": [ { "gen": { "height": 1191119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "790feb4019102515386d80948a54e36906865d74e92caa2e3baf325c3c4fd8ae" } } ], "extra": [ 1, 12, 225, 11, 29, 233, 172, 119, 177, 252, 118, 206, 252, 127, 216, 217, 83, 189, 37, 118, 237, 165, 113, 236, 124, 36, 100, 200, 175, 184, 167, 90, 223, 2, 17, 0, 0, 0, 4, 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