Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dfcbdb12e8fcf8f790f63dccafa5cca1c819a7e44295ef7273394b6b9a06504

Tx prefix hash: a00505c298e39282ae7b78c4bfcaaf0dabd51981be3f3d8ebcaec260d777302e
Tx public key: a6b4587e9aef0275f0078b50d6f42d844dab6e97d4759eebf54aa9cb29daef4b
Timestamp: 1729458438 Timestamp [UCT]: 2024-10-20 21:07:18 Age [y:d:h:m:s]: 00:143:13:51:49
Block: 1135954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102406 RingCT/type: yes/0
Extra: 01a6b4587e9aef0275f0078b50d6f42d844dab6e97d4759eebf54aa9cb29daef4b02110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e4647c1d33c186ff8ace99f5d65d8ce5d94dec917916fd814c55ef9dd5818ba 0.600000000000 1619295 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": 1135964, "vin": [ { "gen": { "height": 1135954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e4647c1d33c186ff8ace99f5d65d8ce5d94dec917916fd814c55ef9dd5818ba" } } ], "extra": [ 1, 166, 180, 88, 126, 154, 239, 2, 117, 240, 7, 139, 80, 214, 244, 45, 132, 77, 171, 110, 151, 212, 117, 158, 235, 245, 74, 169, 203, 41, 218, 239, 75, 2, 17, 0, 0, 0, 12, 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