Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04d35d7ddb8a6239197004682363c537085a413eae5259d212fde6b5ef9365b7

Tx prefix hash: ec39366ccceaf4712bd17a5baf775409e4a06f3af725f6bbeac425b33142bdfd
Tx public key: bf96eb1543276eea40f85c281a6d9d1af8d8444cf0e5a407abb5a402cdd00804
Timestamp: 1743015735 Timestamp [UTC]: 2025-03-26 19:02:15 Age [y:d:h:m:s]: 01:239:18:46:06
Block: 1247864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435582 RingCT/type: yes/0
Extra: 01bf96eb1543276eea40f85c281a6d9d1af8d8444cf0e5a407abb5a402cdd00804021100000006165b77a1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 37751958cff683adfa992cef9c946bee2c6d08cc9e2f936b32b17f21eb3f4ebc 0.000600000000 1734891 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": 1247874, "vin": [ { "gen": { "height": 1247864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37751958cff683adfa992cef9c946bee2c6d08cc9e2f936b32b17f21eb3f4ebc" } } ], "extra": [ 1, 191, 150, 235, 21, 67, 39, 110, 234, 64, 248, 92, 40, 26, 109, 157, 26, 248, 216, 68, 76, 240, 229, 164, 7, 171, 181, 164, 2, 205, 208, 8, 4, 2, 17, 0, 0, 0, 6, 22, 91, 119, 161, 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: