Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 599a9b9861e9be94ae3d36bdf5a8caf2bea67591861e95b6749eb0c8ab74ec8b

Tx prefix hash: 98961a64ec557440b414ec74153e23967b0ffed61fb1d243fab2eb60c1888d95
Tx public key: ae87852f82c03c1324d32e336f9203907a34512d3ebd62f1b486a236db4175d9
Timestamp: 1726347020 Timestamp [UCT]: 2024-09-14 20:50:20 Age [y:d:h:m:s]: 00:117:16:32:33
Block: 1110172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84161 RingCT/type: yes/0
Extra: 01ae87852f82c03c1324d32e336f9203907a34512d3ebd62f1b486a236db4175d9021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0880d765e1c0b033edf331018fa12eba4518abe438cb8e0f5eddf603c787fd7 0.600000000000 1588685 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": 1110182, "vin": [ { "gen": { "height": 1110172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0880d765e1c0b033edf331018fa12eba4518abe438cb8e0f5eddf603c787fd7" } } ], "extra": [ 1, 174, 135, 133, 47, 130, 192, 60, 19, 36, 211, 46, 51, 111, 146, 3, 144, 122, 52, 81, 45, 62, 189, 98, 241, 180, 134, 162, 54, 219, 65, 117, 217, 2, 17, 0, 0, 0, 6, 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