Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4271d99ebbe79c34b6a174c8d3d68a6605df0f09ea74e68c515f35a4e82c26b

Tx prefix hash: 5dd3e0eeb76d5308489977bc5c947c563247ded4d8a46026e579d9fe7c8d2f2a
Tx public key: b2aaf1c60d427894a9d63a167086ac17bf7e6add3b3e5c6dab9604e1c26b3ccf
Timestamp: 1790953813 Timestamp [UTC]: 2026-10-02 15:10:13 Age [y:d:h:m:s]: 00:046:00:26:34
Block: 1646999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 33470 RingCT/type: yes/0
Extra: 01b2aaf1c60d427894a9d63a167086ac17bf7e6add3b3e5c6dab9604e1c26b3ccf

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1550893563f1b9ccb5a8824ac2dafc802d748bc4c30d8c30d0c19f4fd9e9991e 0.000600000000 2137155 of 15 <bf>

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": 1647009, "vin": [ { "gen": { "height": 1646999 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "1550893563f1b9ccb5a8824ac2dafc802d748bc4c30d8c30d0c19f4fd9e9991e", "view_tag": "bf" } } } ], "extra": [ 1, 178, 170, 241, 198, 13, 66, 120, 148, 169, 214, 58, 22, 112, 134, 172, 23, 191, 126, 106, 221, 59, 62, 92, 109, 171, 150, 4, 225, 194, 107, 60, 207 ], "rct_signatures": { "type": 0 } }


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