Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb2f3c92a021a642a915dae95f506be7481c77b84e2c0c8f28845dd97e5aba18

Tx prefix hash: ef42f4aebc6b109f8c781f22c05d357d8e170c088e207c58259511026ceb312f
Tx public key: dc289ef866ec4326b124d3f4a23e4cef9467ae334856267d014705e2e844339c
Timestamp: 1769557175 Timestamp [UTC]: 2026-01-27 23:39:35 Age [y:d:h:m:s]: 00:295:05:14:38
Block: 1465078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216570 RingCT/type: yes/0
Extra: 01dc289ef866ec4326b124d3f4a23e4cef9467ae334856267d014705e2e844339c02110000000249d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1502385427f19327c84ac22acd0e09cf1d39afdedb2707a4058d83540fce352a 0.000600000000 1954304 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": 1465088, "vin": [ { "gen": { "height": 1465078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1502385427f19327c84ac22acd0e09cf1d39afdedb2707a4058d83540fce352a" } } ], "extra": [ 1, 220, 40, 158, 248, 102, 236, 67, 38, 177, 36, 211, 244, 162, 62, 76, 239, 148, 103, 174, 51, 72, 86, 38, 125, 1, 71, 5, 226, 232, 68, 51, 156, 2, 17, 0, 0, 0, 2, 73, 215, 62, 152, 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: