Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c65ac5b9e6696ae8aa2db2f874b41d179ee225ea93252ce3f016bc2d592d2600

Tx prefix hash: 131f115a284e173dc9154e427df67be96d36c0978517d5dcdf13c9ed542449c3
Tx public key: 82fcf20293fd09cf35126321c7cdfe9eaa408baabbbf5f3ca37664ce7dd6f748
Timestamp: 1742585656 Timestamp [UTC]: 2025-03-21 19:34:16 Age [y:d:h:m:s]: 01:242:21:19:36
Block: 1244321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437705 RingCT/type: yes/0
Extra: 0182fcf20293fd09cf35126321c7cdfe9eaa408baabbbf5f3ca37664ce7dd6f74802110000000158cb2e2b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f016c4950e4c894ab559821c47259d4f5d002e7d245cc2ba22da444b4b50b13e 0.000600000000 1731312 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": 1244331, "vin": [ { "gen": { "height": 1244321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f016c4950e4c894ab559821c47259d4f5d002e7d245cc2ba22da444b4b50b13e" } } ], "extra": [ 1, 130, 252, 242, 2, 147, 253, 9, 207, 53, 18, 99, 33, 199, 205, 254, 158, 170, 64, 139, 170, 187, 191, 95, 60, 163, 118, 100, 206, 125, 214, 247, 72, 2, 17, 0, 0, 0, 1, 88, 203, 46, 43, 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: