Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f1a855262ee2d44611fa5f4bfe82e77b419e1fe17feb0fed02f96e9df5947f6

Tx prefix hash: ecb18a871396ac53bbb43e7f4d34973e1755f65ff9c9180d8c382a5b525aee0c
Tx public key: 121a851fc8ef427d9c0c1f35eee2b41591f2245ed230a545734a392471aacf1e
Timestamp: 1760585676 Timestamp [UTC]: 2025-10-16 03:34:36 Age [y:d:h:m:s]: 01:034:11:50:33
Block: 1390910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291066 RingCT/type: yes/0
Extra: 01121a851fc8ef427d9c0c1f35eee2b41591f2245ed230a545734a392471aacf1e0211000000032609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 320d0f1ff398e8e002d84fe756f2cd2eec6afb8096e61b9e041428f192d86b4a 0.000600000000 1879157 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": 1390920, "vin": [ { "gen": { "height": 1390910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "320d0f1ff398e8e002d84fe756f2cd2eec6afb8096e61b9e041428f192d86b4a" } } ], "extra": [ 1, 18, 26, 133, 31, 200, 239, 66, 125, 156, 12, 31, 53, 238, 226, 180, 21, 145, 242, 36, 94, 210, 48, 165, 69, 115, 74, 57, 36, 113, 170, 207, 30, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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: