Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76883ab2ef287fd02eb4c1a7c1bc04e03b660626f515e71ee3bc5d39c13386a4

Tx prefix hash: 6d75abb2edf0cbb566589245ac8a1bfa8c70c3a066a9b59bed45403a05d43aaa
Tx public key: a842d060fc3c7d33e61c61f8bb8ba7f5db19d0b17eb4e123fddadfe827f61cf2
Timestamp: 1744217496 Timestamp [UTC]: 2025-04-09 16:51:36 Age [y:d:h:m:s]: 01:164:05:11:03
Block: 1257829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382103 RingCT/type: yes/0
Extra: 01a842d060fc3c7d33e61c61f8bb8ba7f5db19d0b17eb4e123fddadfe827f61cf20211000000032609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6bcb1b1973c255cf1e2e5b9f77b9cfe2101acf7f89a61b7016cfc77031c700b5 0.000600000000 1744960 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": 1257839, "vin": [ { "gen": { "height": 1257829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bcb1b1973c255cf1e2e5b9f77b9cfe2101acf7f89a61b7016cfc77031c700b5" } } ], "extra": [ 1, 168, 66, 208, 96, 252, 60, 125, 51, 230, 28, 97, 248, 187, 139, 167, 245, 219, 25, 208, 177, 126, 180, 225, 35, 253, 218, 223, 232, 39, 246, 28, 242, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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: