Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae8e70c9b5e1fae48ee2a40359b79cd1fabcf59dd5dd4fe8b25fb59f3d0b4ddc

Tx prefix hash: f4c2e5984a74ba4682bf656f9ad7d9192e6c25827d12177603802940526d22e3
Tx public key: 75a13f86d50e131d291450040e516c7be2719b98e8e6989f21f6655adef858e8
Timestamp: 1715473807 Timestamp [UCT]: 2024-05-12 00:30:07 Age [y:d:h:m:s]: 00:228:03:54:47
Block: 1020061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163291 RingCT/type: yes/0
Extra: 0175a13f86d50e131d291450040e516c7be2719b98e8e6989f21f6655adef858e8021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b690424bea0f96bb8478f3c7017516d8ae838d4852781ebafc51a377a9c11e2f 0.600000000000 1484120 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": 1020071, "vin": [ { "gen": { "height": 1020061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b690424bea0f96bb8478f3c7017516d8ae838d4852781ebafc51a377a9c11e2f" } } ], "extra": [ 1, 117, 161, 63, 134, 213, 14, 19, 29, 41, 20, 80, 4, 14, 81, 108, 123, 226, 113, 155, 152, 232, 230, 152, 159, 33, 246, 101, 90, 222, 248, 88, 232, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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