Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b408734a955268061d7aae551ffc4a1eaef974cd22b2d3de37772ae3caa0171b

Tx prefix hash: dd0f060fad398001b1c53bdb4c7aee63a54e0bc28bec950081f9432e292fcd3d
Tx public key: 3466508d277f9929f7416b1e252740960ab5e8b53d5675eadd6f8eb71e353421
Timestamp: 1741244932 Timestamp [UTC]: 2025-03-06 07:08:52 Age [y:d:h:m:s]: 01:254:19:14:40
Block: 1233226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446103 RingCT/type: yes/0
Extra: 013466508d277f9929f7416b1e252740960ab5e8b53d5675eadd6f8eb71e353421021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 89567c4296241bafbd685a603e28b1e07ca658713804cf6fe821df35d3357fe9 0.000600000000 1720145 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": 1233236, "vin": [ { "gen": { "height": 1233226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89567c4296241bafbd685a603e28b1e07ca658713804cf6fe821df35d3357fe9" } } ], "extra": [ 1, 52, 102, 80, 141, 39, 127, 153, 41, 247, 65, 107, 30, 37, 39, 64, 150, 10, 181, 232, 181, 61, 86, 117, 234, 221, 111, 142, 183, 30, 53, 52, 33, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: