Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53d58d50cae14bff3b1fccbd449bdc12733c92af103482d28bfff27ef66bf9fd

Tx prefix hash: 245da467b0e30f15dafb27660d5e7d6d9acd30ac0891aadf45955e4c2c28b65c
Tx public key: 898ad1099a061ade57bd750545d1a74adb45124e2c021a4b35eb69f18949d0cb
Timestamp: 1741323374 Timestamp [UTC]: 2025-03-07 04:56:14 Age [y:d:h:m:s]: 01:258:00:44:07
Block: 1233877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448562 RingCT/type: yes/0
Extra: 01898ad1099a061ade57bd750545d1a74adb45124e2c021a4b35eb69f18949d0cb0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7eec8d4115dbc87363ef43bb73d51537f7e73e95f39c48f86b2d690c22099a10 0.000600000000 1720802 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": 1233887, "vin": [ { "gen": { "height": 1233877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7eec8d4115dbc87363ef43bb73d51537f7e73e95f39c48f86b2d690c22099a10" } } ], "extra": [ 1, 137, 138, 209, 9, 154, 6, 26, 222, 87, 189, 117, 5, 69, 209, 167, 74, 219, 69, 18, 78, 44, 2, 26, 75, 53, 235, 105, 241, 137, 73, 208, 203, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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: