Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2935f50a64a9ebcc6248e68eaf5398ed61e98a2b463c03c6dcc7515c0e85dac9

Tx prefix hash: 36b525bc8455d4821849e15131f277aacea056b358eee9d4e523c119963c38d4
Tx public key: cc8d5082f695ae1df6117e59e090d132af4ce8da944f7232271aef26106fc7e9
Timestamp: 1710918757 Timestamp [UCT]: 2024-03-20 07:12:37 Age [y:d:h:m:s]: 01:017:10:10:21
Block: 982292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273396 RingCT/type: yes/0
Extra: 01cc8d5082f695ae1df6117e59e090d132af4ce8da944f7232271aef26106fc7e902110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: daa3e45b62b2f31fdd063a628c6130875a6ecc080ce4ce7e98d94655bb2fd654 0.600000000000 1442397 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": 982302, "vin": [ { "gen": { "height": 982292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "daa3e45b62b2f31fdd063a628c6130875a6ecc080ce4ce7e98d94655bb2fd654" } } ], "extra": [ 1, 204, 141, 80, 130, 246, 149, 174, 29, 246, 17, 126, 89, 224, 144, 209, 50, 175, 76, 232, 218, 148, 79, 114, 50, 39, 26, 239, 38, 16, 111, 199, 233, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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