Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c65a922ce0763987a4be039df5ba469b1cf107e11e4ca22b1b6635fac56c245d

Tx prefix hash: d212314c0a26efd1007f877fffd234348520db370bd0dfe136ceef005a5244f2
Tx public key: 390dc2757b78f3c64fb02d4fe466d5fb9a2456cef058e0ece0a03cb4c5be9186
Timestamp: 1580477098 Timestamp [UTC]: 2020-01-31 13:24:58 Age [y:d:h:m:s]: 06:237:00:14:16
Block: 55742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1586103 RingCT/type: yes/0
Extra: 01390dc2757b78f3c64fb02d4fe466d5fb9a2456cef058e0ece0a03cb4c5be9186021100000003391a8d0e000000000000000000

1 output(s) for total of 0.401154752357 xmr

stealth address amount amount idx tag
00: a27c3e8e81f160600fb3f759855edca09e6c0a2bca48dce0ea0a8b1d7dad3b96 0.401154752357 102858 of 0 -

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": 55752, "vin": [ { "gen": { "height": 55742 } } ], "vout": [ { "amount": 401154752357, "target": { "key": "a27c3e8e81f160600fb3f759855edca09e6c0a2bca48dce0ea0a8b1d7dad3b96" } } ], "extra": [ 1, 57, 13, 194, 117, 123, 120, 243, 198, 79, 176, 45, 79, 228, 102, 213, 251, 154, 36, 86, 206, 240, 88, 224, 236, 224, 160, 60, 180, 197, 190, 145, 134, 2, 17, 0, 0, 0, 3, 57, 26, 141, 14, 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: