Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 530e2dbdc93df8fed8673f3898bef00e942ecb70188b51db157b88e2df123f6d

Tx prefix hash: 3cc77ce76f7ab11f7104df9236f7040085c2f678aafe2729a10c6a9622845abb
Tx public key: 6979be7f76e0e7f8040a3de9718642758168eb76187b14f908f3386f2d15b76b
Timestamp: 1759967037 Timestamp [UTC]: 2025-10-08 23:43:57 Age [y:d:h:m:s]: 01:041:06:55:00
Block: 1385781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295918 RingCT/type: yes/0
Extra: 016979be7f76e0e7f8040a3de9718642758168eb76187b14f908f3386f2d15b76b021100000010a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6cb5c1b2f397441c5153447dffcbfd0b10f046379bbc0a8e81d69451ccc455ee 0.000600000000 1873944 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": 1385791, "vin": [ { "gen": { "height": 1385781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cb5c1b2f397441c5153447dffcbfd0b10f046379bbc0a8e81d69451ccc455ee" } } ], "extra": [ 1, 105, 121, 190, 127, 118, 224, 231, 248, 4, 10, 61, 233, 113, 134, 66, 117, 129, 104, 235, 118, 24, 123, 20, 249, 8, 243, 56, 111, 45, 21, 183, 107, 2, 17, 0, 0, 0, 16, 165, 220, 205, 121, 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: