Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e60d6acdd3dab1222ba023f250b1e739bf1b92fc215a7d400b6e6f1f8b5200af

Tx prefix hash: 6d099b59599b48530d510da8565ead9beb7eefe1fbdce027d05a7eef17fb5b93
Tx public key: 0d9e41d1a27d320143d6822c0b099a6a5951d68f6e7edf43381fc6089fde9449
Timestamp: 1694800493 Timestamp [UCT]: 2023-09-15 17:54:53 Age [y:d:h:m:s]: 01:041:12:29:05
Block: 848825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290967 RingCT/type: yes/0
Extra: 010d9e41d1a27d320143d6822c0b099a6a5951d68f6e7edf43381fc6089fde9449021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.945127651000 dcy

stealth address amount amount idx
00: bef2b728bcccec279427811d0d8435a7f2d795c37c91f6ef76c5feda7c0b6428 0.945127651000 1302453 of 0

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": 848835, "vin": [ { "gen": { "height": 848825 } } ], "vout": [ { "amount": 945127651, "target": { "key": "bef2b728bcccec279427811d0d8435a7f2d795c37c91f6ef76c5feda7c0b6428" } } ], "extra": [ 1, 13, 158, 65, 209, 162, 125, 50, 1, 67, 214, 130, 44, 11, 9, 154, 106, 89, 81, 214, 143, 110, 126, 223, 67, 56, 31, 198, 8, 159, 222, 148, 73, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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