Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b545a896c1190c112f19ad7c8c9015363a1e1874ac6b652cda9eec8d169d3ec2

Tx prefix hash: 3cb2213604bbeb8203b6e010e81790ddf1761aa26b393202cd8b5bbf57a59d71
Tx public key: 7a09ef5b9e403b0356a3e99ef77ab4743010b16a38cc0773e12faa2ae9c86f46
Timestamp: 1770255040 Timestamp [UTC]: 2026-02-05 01:30:40 Age [y:d:h:m:s]: 00:287:02:40:53
Block: 1470893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210733 RingCT/type: yes/0
Extra: 017a09ef5b9e403b0356a3e99ef77ab4743010b16a38cc0773e12faa2ae9c86f46021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1cd45dd8b039b0d5e6afa86c2cd3e759d3dfa52c593445a0d242e1a07e534ad8 0.000600000000 1960163 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": 1470903, "vin": [ { "gen": { "height": 1470893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cd45dd8b039b0d5e6afa86c2cd3e759d3dfa52c593445a0d242e1a07e534ad8" } } ], "extra": [ 1, 122, 9, 239, 91, 158, 64, 59, 3, 86, 163, 233, 158, 247, 122, 180, 116, 48, 16, 177, 106, 56, 204, 7, 115, 225, 47, 170, 42, 233, 200, 111, 70, 2, 17, 0, 0, 0, 4, 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: