Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a87a8eb34f60601a6e28d9a8439ad342b910192357d74e3b1d25a77a2a24daf

Tx prefix hash: 79a0bca60c362015480f02ee85c5a4c2bd1c2c304009aee979224c6b81b4b6a8
Tx public key: be4ae2e444a77a26a53294610eed162ca905f29eb6679ebcb8f6f60538873513
Timestamp: 1733830618 Timestamp [UCT]: 2024-12-10 11:36:58 Age [y:d:h:m:s]: 00:103:11:26:18
Block: 1172125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73717 RingCT/type: yes/0
Extra: 01be4ae2e444a77a26a53294610eed162ca905f29eb6679ebcb8f6f60538873513021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b33534af0cfc0039e79e0a87a588aa3c7f2424d533735bc907d9eefcbb2f6cc 0.600000000000 1657976 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": 1172135, "vin": [ { "gen": { "height": 1172125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b33534af0cfc0039e79e0a87a588aa3c7f2424d533735bc907d9eefcbb2f6cc" } } ], "extra": [ 1, 190, 74, 226, 228, 68, 167, 122, 38, 165, 50, 148, 97, 14, 237, 22, 44, 169, 5, 242, 158, 182, 103, 158, 188, 184, 246, 246, 5, 56, 135, 53, 19, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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