Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6aa755bfbcc6c79e76670ccaac40cc38ef5c973f7617cf05fb5581ea843c3a9

Tx prefix hash: 51828b93b899fc74575f7e789c3149917b6f4108ab151afbb222af9414dee98f
Tx public key: 7e431e12b61676653c4dbfeac82b6ff9f9497a3dcc5ef19c1bbe40a8e75e4d43
Timestamp: 1742018531 Timestamp [UTC]: 2025-03-15 06:02:11 Age [y:d:h:m:s]: 01:252:08:00:19
Block: 1239640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443854 RingCT/type: yes/0
Extra: 017e431e12b61676653c4dbfeac82b6ff9f9497a3dcc5ef19c1bbe40a8e75e4d430211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 70c63db8a6cf4bc55dcc822de368c95cc58b2bf302e0be7c4922bedfcfef0f45 0.000600000000 1726605 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": 1239650, "vin": [ { "gen": { "height": 1239640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70c63db8a6cf4bc55dcc822de368c95cc58b2bf302e0be7c4922bedfcfef0f45" } } ], "extra": [ 1, 126, 67, 30, 18, 182, 22, 118, 101, 60, 77, 191, 234, 200, 43, 111, 249, 249, 73, 122, 61, 204, 94, 241, 156, 27, 190, 64, 168, 231, 94, 77, 67, 2, 17, 0, 0, 0, 4, 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: