Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db30a27e509582ca6f5dd491a4cafb8769dd8ab9c2b313773bb009af219a85c4

Tx prefix hash: e89319e7ab3f595b20617d77055817c6f503abf9e5eda2c42f35ca5bc07cee97
Tx public key: ea294ddfa85780602d0ebb7820c29cb23fc6d704c890bbe89d21f94641812dc4
Timestamp: 1740419179 Timestamp [UTC]: 2025-02-24 17:46:19 Age [y:d:h:m:s]: 01:270:05:49:13
Block: 1226368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457126 RingCT/type: yes/0
Extra: 01ea294ddfa85780602d0ebb7820c29cb23fc6d704c890bbe89d21f94641812dc40211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e1d13db75f3ffe5be7b32678600fc0ca7cc76bc4d4cbeadb49b582df689b77b1 0.000600000000 1713239 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": 1226378, "vin": [ { "gen": { "height": 1226368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1d13db75f3ffe5be7b32678600fc0ca7cc76bc4d4cbeadb49b582df689b77b1" } } ], "extra": [ 1, 234, 41, 77, 223, 168, 87, 128, 96, 45, 14, 187, 120, 32, 194, 156, 178, 63, 198, 215, 4, 200, 144, 187, 232, 157, 33, 249, 70, 65, 129, 45, 196, 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): devel-2026-02-02-6303d2a (1.2) | monero version: