Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bfcafd628ebcf737969282619abd35f5828d0e2e317f0ef7b1e2ba37558fba8

Tx prefix hash: 97e13244650e3953c4d97ca95b099b7d0ef2a28aa44afa116b6d4c7836520822
Tx public key: a8d3a0037c9843422837ac5f2900adaed90688c7dee07df6fb9efcc87564ee21
Timestamp: 1763709092 Timestamp [UTC]: 2025-11-21 07:11:32 Age [y:d:h:m:s]: 00:361:15:49:47
Block: 1416783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263923 RingCT/type: yes/0
Extra: 01a8d3a0037c9843422837ac5f2900adaed90688c7dee07df6fb9efcc87564ee21021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4b96daa10ebd2200636f22b0bc35fb3c8be5586cb5af803d575db8972251a06d 0.000600000000 1905304 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": 1416793, "vin": [ { "gen": { "height": 1416783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b96daa10ebd2200636f22b0bc35fb3c8be5586cb5af803d575db8972251a06d" } } ], "extra": [ 1, 168, 211, 160, 3, 124, 152, 67, 66, 40, 55, 172, 95, 41, 0, 173, 174, 217, 6, 136, 199, 222, 224, 125, 246, 251, 158, 252, 200, 117, 100, 238, 33, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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: