Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd627db4d1861d2cdcade3bbceac3805aa0cbfddcd94066e35bbbe1840e5dd6d

Tx prefix hash: 125ffdb079b59da4c7e4e59028bfac153c3dddfd3c698480b37104f5f0e54850
Tx public key: 68f5309b8a8af6a92ee75147752eeb6d2f52366d3c4e1e184c375b5b35f62b12
Timestamp: 1775139654 Timestamp [UTC]: 2026-04-02 14:20:54 Age [y:d:h:m:s]: 00:225:10:30:03
Block: 1511274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166505 RingCT/type: yes/0
Extra: 0168f5309b8a8af6a92ee75147752eeb6d2f52366d3c4e1e184c375b5b35f62b12021100000002e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 07a6a4c9390e4f3b04984d2b39c84b17cdba61b6709016a39258e392e0f1153b 0.000600000000 2001064 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": 1511284, "vin": [ { "gen": { "height": 1511274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07a6a4c9390e4f3b04984d2b39c84b17cdba61b6709016a39258e392e0f1153b" } } ], "extra": [ 1, 104, 245, 48, 155, 138, 138, 246, 169, 46, 231, 81, 71, 117, 46, 235, 109, 47, 82, 54, 109, 60, 78, 30, 24, 76, 55, 91, 91, 53, 246, 43, 18, 2, 17, 0, 0, 0, 2, 227, 215, 220, 159, 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: