Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 561ebc1149ef91dd6711da52d7e4b1ecc92bf6e54390c1839ad299c07876ee28

Tx prefix hash: 1caa4baecabc18b7eaba69f9434c987927cc15036f40048567c8d0ebde351823
Tx public key: f4ecf3b7687cc1a2b0cfb6f97078c89b2eb213c18ae65201adf46e03a213c7f9
Timestamp: 1699774021 Timestamp [UCT]: 2023-11-12 07:27:01 Age [y:d:h:m:s]: 01:104:07:03:09
Block: 889875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335680 RingCT/type: yes/0
Extra: 01f4ecf3b7687cc1a2b0cfb6f97078c89b2eb213c18ae65201adf46e03a213c7f902110000000274c3735f000000000000000000

1 output(s) for total of 0.690994704000 dcy

stealth address amount amount idx
00: a8ced96ca33f93c405c1ae31a8cfd299cdd6aa5b637d263ee4ff1a390e1398a0 0.690994704000 1345892 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": 889885, "vin": [ { "gen": { "height": 889875 } } ], "vout": [ { "amount": 690994704, "target": { "key": "a8ced96ca33f93c405c1ae31a8cfd299cdd6aa5b637d263ee4ff1a390e1398a0" } } ], "extra": [ 1, 244, 236, 243, 183, 104, 124, 193, 162, 176, 207, 182, 249, 112, 120, 200, 155, 46, 178, 19, 193, 138, 230, 82, 1, 173, 244, 110, 3, 162, 19, 199, 249, 2, 17, 0, 0, 0, 2, 116, 195, 115, 95, 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