Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20bcd2ade7ec514a20d8d358059781fcd17cad68fd9286f7286566122ba8d9ba

Tx prefix hash: 88ab28458c58151d826c43b0c6e025a0bdd953620f36600d09cf52e2d40d31f9
Tx public key: 5e190f8557a964c2a0b9c298faea662927157ba284995699743dd1931571c374
Timestamp: 1772815022 Timestamp [UTC]: 2026-03-06 16:37:02 Age [y:d:h:m:s]: 00:257:14:28:42
Block: 1492055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189659 RingCT/type: yes/0
Extra: 015e190f8557a964c2a0b9c298faea662927157ba284995699743dd1931571c374021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 08d1d1fec43a8a61eca617b294e87b06a1361a4765ab09a8c6efc6bde18b1f14 0.000600000000 1981593 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": 1492065, "vin": [ { "gen": { "height": 1492055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08d1d1fec43a8a61eca617b294e87b06a1361a4765ab09a8c6efc6bde18b1f14" } } ], "extra": [ 1, 94, 25, 15, 133, 87, 169, 100, 194, 160, 185, 194, 152, 250, 234, 102, 41, 39, 21, 123, 162, 132, 153, 86, 153, 116, 61, 209, 147, 21, 113, 195, 116, 2, 17, 0, 0, 0, 6, 241, 136, 200, 168, 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: