Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc22e82ab1339e39585bbf481a10580e0e07f477a4e5f7210f6cf9fb913990c2

Tx prefix hash: f59ce3857731ca827d131ddb453c3bce572a277368152b8a73167e29837e937e
Tx public key: e05859b1aaba358174ef0c0eef4c75e75adc74e38662c8a4b28fe9dbbfbe1d9c
Timestamp: 1742289469 Timestamp [UTC]: 2025-03-18 09:17:49 Age [y:d:h:m:s]: 01:246:01:06:20
Block: 1241883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439933 RingCT/type: yes/0
Extra: 01e05859b1aaba358174ef0c0eef4c75e75adc74e38662c8a4b28fe9dbbfbe1d9c021100000007007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b6a414a5298a03f0ea30ad86f4db02c55245c629e3504e8fdd09eb5ec86bf1d7 0.000600000000 1728856 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": 1241893, "vin": [ { "gen": { "height": 1241883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6a414a5298a03f0ea30ad86f4db02c55245c629e3504e8fdd09eb5ec86bf1d7" } } ], "extra": [ 1, 224, 88, 89, 177, 170, 186, 53, 129, 116, 239, 12, 14, 239, 76, 117, 231, 90, 220, 116, 227, 134, 98, 200, 164, 178, 143, 233, 219, 191, 190, 29, 156, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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: