Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 698ed5ee2d83d2fee5afb210201f2ebd9c7ea8573678bdb8ff7a79cb1e57fbf6

Tx prefix hash: 56804cecfad34bd1b6933769aa551ffb255096c3a6a7a7f65cd453240fa8089f
Tx public key: 59c44d2bb0999987e8e81603943f1bd5ae7d86aa257f3bcd665e04b3e1f60d69
Timestamp: 1737338415 Timestamp [UTC]: 2025-01-20 02:00:15 Age [y:d:h:m:s]: 01:300:07:44:25
Block: 1201103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478457 RingCT/type: yes/0
Extra: 0159c44d2bb0999987e8e81603943f1bd5ae7d86aa257f3bcd665e04b3e1f60d690211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ad6ad02f5fe5e06ac37bfec36a26abf845384c4a6ac3a8bafa9b9d3cac71f6ba 0.000600000000 1687752 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 dinastycoin-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": 1201113, "vin": [ { "gen": { "height": 1201103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad6ad02f5fe5e06ac37bfec36a26abf845384c4a6ac3a8bafa9b9d3cac71f6ba" } } ], "extra": [ 1, 89, 196, 77, 43, 176, 153, 153, 135, 232, 232, 22, 3, 148, 63, 27, 213, 174, 125, 134, 170, 37, 127, 59, 205, 102, 94, 4, 179, 225, 246, 13, 105, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: