Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a2166249a36a8270f49a1e1242c5277e3fac0711fb930087adfa628b3bd5a68

Tx prefix hash: 252c6f9612fd7a668310eb6d82ae3fb31ffaa285e6e182bc1705ea9eb0eef74e
Tx public key: 9343ad71e8e84554f61f531597c95b3f4d63c038185b60f3e183513d2744b145
Timestamp: 1748807917 Timestamp [UCT]: 2025-06-01 19:58:37 Age [y:d:h:m:s]: 00:171:06:16:47
Block: 1295835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120102 RingCT/type: yes/0
Extra: 019343ad71e8e84554f61f531597c95b3f4d63c038185b60f3e183513d2744b145021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8f814c0e8acabf97b3309af676bdb42096c44ae4e1491d6fb1349c791e05022 0.600000000000 1783342 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 dinasty-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": 1295845, "vin": [ { "gen": { "height": 1295835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8f814c0e8acabf97b3309af676bdb42096c44ae4e1491d6fb1349c791e05022" } } ], "extra": [ 1, 147, 67, 173, 113, 232, 232, 69, 84, 246, 31, 83, 21, 151, 201, 91, 63, 77, 99, 192, 56, 24, 91, 96, 243, 225, 131, 81, 61, 39, 68, 177, 69, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8