Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b510813dc5cd8d4bea82606158a8467479c84adc4d2ea7fb51246ae1e1bbaf71

Tx prefix hash: 08279a194f83d0fa6675631a4920715e8d80cec544b792eb7bef3c0014d01a7f
Tx public key: dc7c5eea6170fba50af4ee8c3fad3b81ac7627db39d9679b01b455808f506a82
Timestamp: 1729110608 Timestamp [UCT]: 2024-10-16 20:30:08 Age [y:d:h:m:s]: 00:229:18:35:51
Block: 1133084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164050 RingCT/type: yes/0
Extra: 01dc7c5eea6170fba50af4ee8c3fad3b81ac7627db39d9679b01b455808f506a82021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c34edaae095a37aa7080591e07c6457c189746257bbf6e61123813dc8da20cc 0.600000000000 1616153 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": 1133094, "vin": [ { "gen": { "height": 1133084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c34edaae095a37aa7080591e07c6457c189746257bbf6e61123813dc8da20cc" } } ], "extra": [ 1, 220, 124, 94, 234, 97, 112, 251, 165, 10, 244, 238, 140, 63, 173, 59, 129, 172, 118, 39, 219, 57, 217, 103, 155, 1, 180, 85, 128, 143, 80, 106, 130, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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