Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7840be96f84bd27c998dfd2379e7f01ac0ee50f5667b82be102b5bd1c052393b

Tx prefix hash: 52940e19afffbeef7ca7d9a0bd87e450ae55024f7aaa3f4345c014230f32a241
Tx public key: a21f9a5e266047853909704529bbea1e626b5df2268184cccfdea71f7a09327b
Timestamp: 1757320101 Timestamp [UTC]: 2025-09-08 08:28:21 Age [y:d:h:m:s]: 00:322:15:24:32
Block: 1363939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235974 RingCT/type: yes/0
Extra: 01a21f9a5e266047853909704529bbea1e626b5df2268184cccfdea71f7a09327b021100000007ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 356eda421b3fa26f2748c3fb7d7f6de9c9f58d8c84b968aba03caa1f0121176a 0.000600000000 1851978 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": 1363949, "vin": [ { "gen": { "height": 1363939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "356eda421b3fa26f2748c3fb7d7f6de9c9f58d8c84b968aba03caa1f0121176a" } } ], "extra": [ 1, 162, 31, 154, 94, 38, 96, 71, 133, 57, 9, 112, 69, 41, 187, 234, 30, 98, 107, 93, 242, 38, 129, 132, 204, 207, 222, 167, 31, 122, 9, 50, 123, 2, 17, 0, 0, 0, 7, 173, 121, 72, 208, 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: