Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50ecf94dc774ed9f3684987540d1a117148d9467cba24d8b9ed91878bd0638c1

Tx prefix hash: 90cbd0a6574fda49d2da44087e2cdd2cc84d61a1ef72381b1f728b05f5e6a13c
Tx public key: 09a50e13f8919ec7c886a8d403d9b4e6695343caa5d955d6a6e43206834ba92a
Timestamp: 1733450956 Timestamp [UCT]: 2024-12-06 02:09:16 Age [y:d:h:m:s]: 00:158:06:57:41
Block: 1168969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112958 RingCT/type: yes/0
Extra: 0109a50e13f8919ec7c886a8d403d9b4e6695343caa5d955d6a6e43206834ba92a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a18876c7e53be11e3f5cc87e97da2f89ef4a1d296a0cd980904a568eccbe0db 0.600000000000 1654682 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": 1168979, "vin": [ { "gen": { "height": 1168969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a18876c7e53be11e3f5cc87e97da2f89ef4a1d296a0cd980904a568eccbe0db" } } ], "extra": [ 1, 9, 165, 14, 19, 248, 145, 158, 199, 200, 134, 168, 212, 3, 217, 180, 230, 105, 83, 67, 202, 165, 217, 85, 214, 166, 228, 50, 6, 131, 75, 169, 42, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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